Windows Virtual Desktop became Azure Virtual Desktop
In June 2021, Microsoft renamed Windows Virtual Desktop to Azure Virtual Desktop (AVD).

Updated note (2026): Azure Virtual Desktop (AVD) is the current product name. Azure Active Directory referenced in this historical announcement is now Microsoft Entra ID.
Microsoft announced in June 2021 that Windows Virtual Desktop (WVD) would be rebranded as Azure Virtual Desktop (AVD).
The rebrand reflected Microsoft’s broader positioning of the service as a cloud VDI and application-delivery platform for hybrid work. For enterprise architecture, the meaningful point was not simply the product name: AVD became an increasingly important platform workload requiring secure identity integration, scalable host management, profile storage, endpoint controls and monitoring.
At announcement time, Microsoft also described new capabilities and pricing options for remote application streaming.
Some of the capabilities discussed in that historical announcement included:
Enhanced Support for Microsoft Entra ID
- Microsoft Entra ID, then named Azure Active Directory, is a critical service used by organizations to manage user access to important apps and data and maintain strong security controls. At announcement time, Microsoft also described support for joining Azure Virtual Desktop virtual machines directly to that identity service.
Multi-Session Management
- Microsoft Endpoint Manager allows you to manage policies and distribute applications across devices.
Microsoft’s original announcement is available in Azure Virtual Desktop: The desktop and app virtualization platform for the hybrid workplace.
Summary
Azure Virtual Desktop is now the established product name. For new deployments, focus on current AVD documentation and design the service as part of a governed Azure platform: identity, network paths, image management, user profiles, monitoring and operational ownership should be explicit from the start.
Follow Azure architecture notes
Follow new Azure architecture notes via RSS or connect with me on LinkedIn. Public technical work is also available on GitHub.